Skip to content

fix: keep underscores in enum names with numbers (like ENUM_123_VALUE) #1260

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jun 8, 2025

Conversation

parsaghk
Copy link
Contributor

@parsaghk parsaghk commented May 30, 2025

Hi 👋

Before, enum names like ENUM_123_VALUE lost their underscores and became ENUM123VALUE.
This change keeps the underscores so the names stay correct. (Fixes #276)

Best,
Parsa

Copy link

changeset-bot bot commented May 30, 2025

🦋 Changeset detected

Latest commit: 5f1586d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
swagger-typescript-api Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@parsaghk parsaghk requested a review from smorimoto June 7, 2025 15:32
@smorimoto
Copy link
Collaborator

Could you please add changeset as well?

@smorimoto smorimoto merged commit 31b628f into acacode:main Jun 8, 2025
3 checks passed
@github-actions github-actions bot mentioned this pull request Jun 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Broken/unexpected behavior for enum values with numbers in them
2 participants